home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
cbv226.zip
/
CBV2.ASC
< prev
next >
Wrap
Text File
|
1990-01-09
|
3KB
|
48 lines
<Press P to Pause or S to Stop>
Why CBV?
Usually, if a Sysop wants to run a reasonable BBS, he or she
must implement some sort of security and a way of double-checking, or
verifying new users so that each account on the BBS belongs to one
real person, and each person has only one account.
The popular method of security and verification is set up so
that new users have restricted access to the system (usually new users
aren't allowed to post public messages, upload, and download). The
sysop calls the phone number that the new user entered. If all goes
well, the number checks out and the Sysop gives the user normal membership
access. The conversation is usually a pleasant experience for both
the sysop and the new user, and the Sysop can check for duplicate
numbers in the event a user tries to gain more than one membership.
Unfortunately, some users call and leave bad phone numbers.
It doesn't matter whether the user is hoping to join the system
without the sysop trying the bad number or is just trying to annoy the
sysop. Either way, it is just wasted time on the sysop's part. This
is usually what happens first on a younger BBS.
After a while, these "twits" start trying other tactics. They
pick a name and number at random out of the phone book, then they log
in as a new user using this false name and number, but the number is
"good" in that it matches up with a real live person. It can fool
some sysops that only check the phone book to match up the name and
number, but for most sysops who actually call the numbers, a huge
misunderstanding may take place between a soon-to-be-frustrated sysop
and a confused innocent person who usually doesn't have anything to do
with computers.
Yet another strategy appears. The new user logs in and makes
up, or even worse, looks up a long-distance phone number. Some sysops
make it standard new user policy to call the number collect. You can
imagine the misunderstanding that often takes place! Other sysops
call with their own money only to find they've wasted fifty cents on
one of a long list of bad long-distance phone numbers.
As if all this isn't enough trouble, even many of the valid
numbers can add to the problem. Often nobody is home at the number or
the number is constantly busy.
All this calling about, wrong numbers, no-answers, and busy
signals add up to quite a bit of time if not money wasted on wrong
long-distance numbers. Not to mention the honest users that have to
pay by waiting and waiting for the sometimes discouraged sysop to
finally get around to trying their number.
So what's the burnt-out sysop to do, short of pulling the
plug? Many do just that when things start getting bad. Automated
Call-Back Verification offers an alternative - It's instant, rarely
requires sysop intervention, relatively painless (maybe even pleasant),
and it keeps the modem-scum out!